Birmingham City Council
Tree preservation zone
There is a problem
- 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset
THE BIRMINGHAM (LAND REAR OF MICHAEL DRIVE, FORMERLY PART OF SPRING COTTAGE, WELLINGTON ROAD, EDGBASTON) TPO 1988
- reference
- 530
- name
- THE BIRMINGHAM (LAND REAR OF MICHAEL DRIVE, FORMERLY PART OF SPRING COTTAGE, WELLINGTON ROAD, EDGBASTON) TPO 1988
- tree-preservation-order
- TPO 530
- tree-preservation-zone-type
- area
- geometry
- MULTIPOLYGON (((-1.907599 52.462039,-1.907391 52.461914,-1.907309 52.461851,-1.907295 52.461822,-1.907203 52.461805,-1.907056 52.461706,-1.906514 52.461523,-1.906208 52.461886,-1.906742 52.462144,-1.906864 52.462241,-1.906925 52.462261,-1.906973 52.462264,-1.907599 52.462039)))
- point
- POINT (-1.906857 52.46191)
- notes
- The shaded area represents those properties which fall within the outline of a Tree Preservation Order. To precisely identify trees protected by the Order, you can request a copy of the tree preservation order at the following link.
- organisation
- entry-date
- 2025-11-30
- start-date
- end-date
How to fix this issue
Your dataset is missing the tree-preservation-order column.
The Tree preservation zone guidance explains how to fix the issue:
tree-preservation-order
The reference for the tree preservation order that covers this zone.
How to improve Birmingham City Council’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL